|
|
| Author |
Thread Statistics | Show CCP posts - 40 post(s) |
|
CCP Veritas
C C P
C C P Alliance
471
   |
Posted - 2012.05.02 14:25:00 -
[1] - Quote
Aryth wrote:TIDI makes the Blackscreening issue much worse.
We've tracked down a likely cause for this, and it's related to how the emergency hot-patch was done. Did you guys continue to experience this problem after Saturday's downtime?
CCP Veritas - Senior Programmer - EVE Software |
|
|
CCP Veritas
C C P
C C P Alliance
472
|
Posted - 2012.05.02 14:39:00 -
[2] - Quote
Aryth wrote:CCP Veritas wrote:Aryth wrote:TIDI makes the Blackscreening issue much worse. We've tracked down a likely cause for this, and it's related to how the emergency hot-patch was done. Did you guys continue to experience this problem after Saturday's downtime? Yes. It was an issue the entire weekend. Very similar to the old 0.0 issues where you never load grid and are dead before you do.
Well damn, time to keep up the search then. If you happen to have any known instances with char names and times please eve-mail me.
Vile rat wrote:If you want to smug it up in this thread you go right ahead ok?
Got most of that out of my system at Fanfest 
CCP Veritas - Senior Programmer - EVE Software |
|
|
CCP Veritas
C C P
C C P Alliance
474
|
Posted - 2012.05.02 14:54:00 -
[3] - Quote
Thomas Kreshant wrote:Just a few questions if you don't mind.
So we obviously had the population cap on the system as mentioned in the blog this as I doubt a whole lot of market trade was happening that day was it still needed due to crimewatch not really scaling well in highsec ?
Given the server needed a population cap if high sec players had filled the system with warm bodies then Burn Jita wouldn't have happened at all?
If that's the case will the reworking of Crimewatch that is occuring improve it's performance enough to rid highsec of population caps?
The majority of the ambient load in Jita on a normal day is due to player movements - jumping in/out, docking/undocking and switching ships (voluntarily or otherwise). These are fairly expensive actions, and since they were still happening in large number during the event, I'm fairly safe assuming that they were a bulk of the ambient load in this event as well. We have a project in the pipe for solving this load.
The refactoring of Crimewatch should help the spikes come down a fair bit as well, so I suspect that a similar event done in, say, a year from now should have a very different performance characteristic.
CCP Veritas - Senior Programmer - EVE Software |
|
|
CCP Veritas
C C P
C C P Alliance
478
|
Posted - 2012.05.02 15:07:00 -
[4] - Quote
Aebe Amraen wrote:Quote:We wanted to keep things fairly low at this point as we had found a few bugs in how Crime Watch worked under Time Dilation. Can we get some details on this bug? Specifically, Friday morning (EVE time) I was hanging out in Jita killing GCC folks, and somehow got concorded without receiving a warning popup before shooting. The person I got concorded for supposedly killing (sec status drops for both aggression and killing) doesn't show up on my kill log. I petitioned it but haven't yet received a reply. Any chance this is related?
Quite possible. Petitioning is the right route, the GMs are aware of what was going on. I'm sure their queue is mildly impressive after all this 
CCP Veritas - Senior Programmer - EVE Software |
|
|
CCP Veritas
C C P
C C P Alliance
495
|
Posted - 2012.05.02 22:08:00 -
[5] - Quote
malaire wrote:What about a case where person coming back to system still has some GCC time left, but less than what is cached in other clients?
That case was already properly handled by sending out an updated time to everyone. It was only the case where the time had been burned off completely that wasn't being handled properly.
CCP Veritas - Senior Programmer - EVE Software |
|
|
|
| |
|